WordPress takes control of ACF: a risky precedent for popular plugins?
While there are no immediate changes for ACF users, the acquisition raises questions about the future of the WordPress ecosystem and whether other popular plugins could follow suit. It highlights the fine line between expanding WordPress’s capabilities and consolidating control over its open-source community.
What happened with Advanced Custom Fields?
In a highly controversial move, WordPress.org took control of the free version of the Advanced Custom Fields (ACF) plugin, removing it from the WordPress plugin directory. This unprecedented action was met with surprise and concern, as the original ACF development team was not consulted. WordPress.org has since replaced the plugin with a forked version called Secure Custom Fields. A fork, in simple terms, refers to taking the original plugin’s code and creating a new, modified version. The original ACF team retains control over the paid version, but this development has sparked significant discussion about WordPress’s future role in third-party plugins.
A new era for plugin acquisition?
Historically, WordPress has embraced an open-source philosophy that encourages diverse development and competition among third-party plugin developers. This flexible and decentralised model, which allows a wide range of plugins to thrive, is mainly responsible for WordPress’s success.
However, the ACF takeover has sparked concerns about WordPress’s future direction. While it may signal a shift toward targeting popular plugins, Matt Mullenweg assured that this was an “unusual situation” due to WP Engine’s legal actions, adding that such interventions would remain rare.
No immediate changes for ACF users
There are no immediate changes for those who rely on ACF, especially the paid version used by many Sumobaby customers.
The plugin’s features, functionality, and pricing will remain the same, and the team behind ACF has committed to keeping its development on track. This reassurance aims to ease user concerns about potential disruptions to their websites.
However, scepticism persists. When a large platform acquires a popular plugin, it’s natural to question whether the long-term plans will stay true to the original vision. While the ACF team has promised to maintain the current pricing and licensing model, some users fear that future updates could incorporate significant changes.
What does this mean for other plugins?
The takeover of ACF raises concerns about the future of WordPress plugin development. While integration and resources may improve, developers risk losing independence or facing shifting priorities. WordPress, however, emphasised that this situation was exceptional. The platform’s plugin guidelines give WordPress the right to intervene for public safety, but they assured developers that similar takeovers are not anticipated unless under extraordinary circumstances.
Potential risks
The precedent set by the ACF acquisition could have far-reaching effects on the open-source community that powers WordPress.
If acquisitions extend to other popular plugins, the platform’s independent and innovative nature might be compromised. The open-source environment could become less vibrant if major plugins fall under WordPress’s control.
Additionally, it might discourage new developers from creating unique solutions, knowing that the platform could eventually absorb the most successful plugins.
Conslusion
WordPress’s acquisition of ACF is a landmark moment, signalling a possible shift in the platform’s approach to third-party plugins. For now, ACF users, including those using the paid version, are not experiencing any immediate impact. However, this acquisition sets a new and potentially risky precedent, raising questions about the future of other plugins in the WordPress ecosystem.
If you have any questions about these developments, please don’t hesitate to reach out to us directly.
